v0.13.5

Compare Source

Patch Changes

• #​13077 11c77b7 Thanks @​penalosa! - fix: runInDurableObject now correctly returns redirect responses (3xx) from Durable Object callbacks instead of throwing "Expected callback for X" errors

• #​13056 8384743 Thanks @​penalosa! - fix: Support dynamic import() inside entrypoint and Durable Object handlers

  Previously, calling exports.default.fetch() or SELF.fetch() on a worker whose handler used a dynamic import() would hang and fail with "Cannot perform I/O on behalf of a different Durable Object". This happened because the module runner's transport — which communicates over a WebSocket owned by the runner Durable Object — was invoked from a different DO context.

  The fix patches the module runner's transport via the onModuleRunner hook so that all invoke() calls are routed through the runner DO's I/O context, regardless of where the import() originates.

• #​13074 4618c05 Thanks @​penalosa! - fix: only apply module fallback extension probing for require(), not import

  The module fallback service previously tried adding .js, .mjs, .cjs, and .json suffixes to extensionless specifiers unconditionally. Per the Node.js spec, this extension-probing behaviour is specific to CommonJS require(). ESM import statements must include explicit file extensions.

  Extension-less TypeScript import specifiers continue to work correctly — they are resolved by Vite's resolver rather than the fallback's extension loop.

• #​13073 baec845 Thanks @​penalosa! - Add adminSecretsStore() to cloudflare:test for seeding secrets in tests

  Secrets store bindings only expose a read-only .get() method, so there was previously no way to seed secret values from within a test. The new adminSecretsStore() helper returns Miniflare's admin API for a secrets store binding, giving tests full control over create, update, and delete operations.

  import { adminSecretsStore } from "cloudflare:test";
  import { env } from "cloudflare:workers";
  
  const admin = adminSecretsStore(env.MY_SECRET);
  await admin.create("test-value");
  
  const value = await env.MY_SECRET.get(); // "test-value"

• #​13083 cfd513f Thanks @​penalosa! - Add a 30-second timeout to waitUntil promise draining to prevent hanging tests

  Previously, if a ctx.waitUntil() promise never resolved, the test suite would hang indefinitely after the test file finished. Now, any waitUntil promises that haven't settled within 30 seconds are abandoned with a warning, allowing the test suite to continue. This aligns with the production waitUntil limit.

• Updated dependencies [eeaa473, 9fcdfca, bc24ec8, 1faff35, 0b4c21a, 535582d, 992f9a3, f4ea4ac, 91b7f73, f6cdab2, 53ed15a, ce65246, 7a5be20, 6b50bfa, 0386553, 9c5ebf5, 53ed15a, 53ed15a]:

  • wrangler@​4.78.0
  • miniflare@​4.20260317.3

v0.13.4

Compare Source

Patch Changes

• #​12999 f9728fd Thanks @​hiendv! - chore: update some tests and fixtures to Vitest 4 / vpw 0.13.x

• Updated dependencies [593c4db, b8f3309, 451dae3, 5aaaab2, 5aaaab2, f8516dd, 9c9fe30, 379f2a2, c2e9163, 6a6449e, 9a1cf29, 875da60]:

  • wrangler@​4.77.0
  • miniflare@​4.20260317.2

v0.13.3

Compare Source

Patch Changes

• #​12881 8729f3d Thanks @​pombosilva! - Workflows testing util waitForStatus now supports waiting for "terminated" and "paused" states.

• Updated dependencies [782df44, 3c988e2, 62545c9, cb71403, 71ab981, 3a1c149, 7c3c6c6, ce48b77, 8729f3d]:

  • wrangler@​4.76.0
  • miniflare@​4.20260317.1

v0.13.2

Compare Source

Patch Changes

• Updated dependencies [c9b3184, 13df6c7, df0d112, 81ee98e, c600ce0, f509d13, 3b81fc6, 0a7fef9]:
  • wrangler@​4.75.0
  • miniflare@​4.20260317.0

v0.13.1

Compare Source

Patch Changes

• Updated dependencies [ade0aed, 2b9a186, 65f1092, 7b0d8f5, 351e1e1, 2b9a186]:
  • miniflare@​4.20260312.1
  • wrangler@​4.74.0

v0.13.0

Compare Source

Minor Changes

• #​11632 a6ddbdb Thanks @​penalosa! - Support Vitest 4 in @cloudflare/vitest-pool-workers.

  This a breaking change to the @cloudflare/vitest-pool-workers integration in order to support Vitest v4. Along with supporting Vitest v4 (and dropping support for Vitest v2 and v3), we've made a number of changes that may require changes to your tests. Our aim has been to improve stability & the foundations of @cloudflare/vitest-pool-workers as we move towards a v1 release of the package.

  We've made a codemod to make the migration easier, which will make the required changes to your config file:

  npx jscodeshift -t node_modules/@​cloudflare/vitest-pool-workers/dist/codemods/vitest-v3-to-v4.mjs vitest.config.ts

  Or, without installing the package first:

  npx jscodeshift -t https://unpkg.com/@​cloudflare/vitest-pool-workers/dist/codemods/vitest-v3-to-v4.mjs --parser=ts vitest.config.ts

  • Config API: defineWorkersProject and defineWorkersConfig from @cloudflare/vitest-pool-workers/config have been replaced with a cloudflareTest() Vite plugin exported from @cloudflare/vitest-pool-workers. The test.poolOptions.workers options are now passed directly to cloudflareTest():

    Before:

    import { defineWorkersProject } from "@​cloudflare/vitest-pool-workers/config";
    
    export default defineWorkersProject({
      test: {
        poolOptions: {
          workers: {
            wrangler: { configPath: "./wrangler.jsonc" },
          },
        },
      },
    });

    After:

    import { cloudflareTest } from "@​cloudflare/vitest-pool-workers";
    import { defineConfig } from "vitest/config";
    
    export default defineConfig({
      plugins: [
        cloudflareTest({
          wrangler: { configPath: "./wrangler.jsonc" },
        }),
      ],
    });

  • isolatedStorage & singleWorker: These have been removed in favour of a simpler isolation model that more closely matches Vitest. Storage isolation is now on a per test file basis, and you can make your test files share the same storage by using the Vitest flags --max-workers=1 --no-isolate

  • import { env, SELF } from "cloudflare:test": These have been removed in favour of import { env, exports } from "cloudflare:workers". exports.default.fetch() has the same behaviour as SELF.fetch(), except that it doesn't expose Assets. To test your assets, write an integration test using startDevWorker()

  • import { fetchMock } from "cloudflare:test": This has been removed. Instead, mock globalThis.fetch or use ecosystem libraries like MSW (recommended).

  • Vitest peer dependency: @cloudflare/vitest-pool-workers now requires vitest@^4.1.0.

Patch Changes

• Updated dependencies [f7de0fd, ff543e3, 8e89e85, e63539d, 8d1e130, 6ee18e1, ecc7f79, 1dda1c8, 4bb61b9]:
  • miniflare@​4.20260312.0
  • wrangler@​4.73.0

v0.12.21

Compare Source

Patch Changes

• #​12790 5451a7f Thanks @​petebacondarwin! - Bump devalue to ^5.6.3 to address security vulnerabilities

  Devalue had denial of service and prototype pollution vulnerabilities. This is a bundled dependency.

• Updated dependencies [5451a7f, 5451a7f, 82cc2a8, 3c67c2a, d645594, 211d75d, 6ed249b, 9f93b54, de65c58, cb14820, a7c87d1, b8c33f5, e4d9510]:

  • miniflare@​4.20260310.0
  • wrangler@​4.72.0

v0.12.20

Compare Source

Patch Changes

• Updated dependencies [ec2459e]:
  • wrangler@​4.71.0
  • miniflare@​4.20260301.1

v0.12.19

Compare Source

Patch Changes

• #​12682 b5b91c9 Thanks @​hiendv! - Fix resource leak where remote proxy sessions were not disposed during pool shutdown, causing vitest processes to hang.

• Updated dependencies [6a8aa5f, d672e2e, 35b2c56, 5f7aaf2, 209b396, 23a365a, 596b8a0, 00e729e, 0769056, 150ef7b, bf9cb3d]:

  • wrangler@​4.70.0
  • miniflare@​4.20260301.1

v0.12.18

Compare Source

Patch Changes

• Updated dependencies [99037e3, 295297a, f765244, c0e9e08]:
  • miniflare@​4.20260305.0
  • wrangler@​4.69.0

v0.12.17

Compare Source

Patch Changes

• Updated dependencies [3d6e421, 294297e]:
  • wrangler@​4.68.1
  • miniflare@​4.20260302.0

v0.12.16

Compare Source

Patch Changes

• Updated dependencies [8d882fa, 8d882fa]:
  • wrangler@​4.68.0

v0.12.15

Compare Source

Patch Changes

• #​12602 58a4020 Thanks @​anonrig! - Optimize filesystem operations by using Node.js's throwIfNoEntry: false option

  This reduces the number of system calls made when checking for file existence by avoiding the overhead of throwing and catching errors for missing paths. This is an internal performance optimization with no user-visible behavioral changes.

• Updated dependencies [e93dc01, c2ed7c2, d920811, 896734d, ebdbe52, 58a4020, 6f6cd94]:

  • wrangler@​4.67.1
  • miniflare@​4.20260302.0

v4.20260317.1

Compare Source

v4.20260316.1

Compare Source

v4.20260313.1

Compare Source

v4.20260312.1

Compare Source

v4.20260310.1

Compare Source

v4.20260307.1

Compare Source

v4.20260306.1

Compare Source

v4.20260305.1

Compare Source

v4.20260305.0

Compare Source

v4.20260304.0

Compare Source

v4.20260303.0

Compare Source

v4.20260302.0

Compare Source

v4.20260301.1

Compare Source

v4.20260228.1

Compare Source

v9.39.4

Compare Source

v0.214.0

Compare Source

v0.213.0

Compare Source

v10.46.0

Compare Source

Important Changes

• feat(elysia): @sentry/elysia - Alpha Release (#​19509)

  New Sentry SDK for the Elysia web framework, supporting both Bun and Node.js runtimes.

  Note: This is an alpha release. Please report any issues or feedback on GitHub.

  Features

  • Automatic error capturing — 5xx errors captured via global onError hook; 3xx/4xx ignored by default. Customizable with shouldHandleError.
  • Automatic tracing — Lifecycle spans for every Elysia phase (Request, Parse, Transform, BeforeHandle, Handle, AfterHandle, MapResponse, AfterResponse, Error) with parameterized route names (e.g. GET /users/:id).
  • Distributed tracing — sentry-trace and baggage headers propagated automatically on incoming/outgoing requests.

  Usage

  import * as Sentry from '@​sentry/elysia';
  import { Elysia } from 'elysia';
  
  Sentry.init({ dsn: '__DSN__', tracesSampleRate: 1.0 });
  
  const app = Sentry.withElysia(new Elysia());
  app.get('/', () => 'Hello World');
  app.listen(3000);

Other Changes

• feat(nuxt): Conditionally use plugins based on Nitro version (v2/v3) (#​19955)
• fix(cloudflare): Forward ctx argument to Workflow.do user callback (#​19891)
• fix(cloudflare): Send correct events in local development (#​19900)
• fix(core): Do not overwrite user provided conversation id in Vercel (#​19903)
• fix(core): Preserve .withResponse() on Anthropic instrumentation (#​19935)
• fix(core): Send internal_error as span status for Vercel error spans (#​19921)
• fix(core): Truncate content array format in Vercel (#​19911)
• fix(deps): bump fast-xml-parser to 5.5.8 in @​azure/core-xml chain (#​19918)
• fix(deps): bump socket.io-parser to 4.2.6 to fix CVE-2026-33151 (#​19880)
• fix(nestjs): Add node to nest metadata (#​19875)
• fix(serverless): Add node to metadata (#​19878)

Work in this release was contributed by @​roli-lpci. Thank you for your contributions!

Bundle size 📦

v10.45.0

Compare Source

Important Changes

• feat(remix): Server Timing Headers Trace Propagation (#​18653)

  The Remix SDK now supports automatic trace propagation via Server-Timing response headers to continue pageload traces on the client side.
  This means, you no longer have to define a custom meta function to add Sentry <meta> tags to your page as previously.
  We'll update out Remix tracing docs after this release.

Other Changes

• fix(cloudflare): Use correct env types for withSentry (#​19836)
• fix(core): Align error span status message with core SpanStatusType for langchain/google-genai (#​19863)
• fix(deno): Clear pre-existing OTel global before registering TracerProvider (#​19723)
• fix(nextjs): Skip tracing for tunnel requests (#​19861)
• fix(node-core): Recycle propagationContext for each request (#​19835)
• ref(core): Simplify core utility functions for smaller bundle (#​19854)

v10.44.0

Compare Source

Important Changes

• feat(effect): Add @sentry/effect SDK (Alpha) (#​19644)

  This release introduces @sentry/effect, a new SDK for Effect.ts applications. The SDK provides Sentry integration via composable Effect layers for both Node.js and browser environments.

  Compose the effectLayer with optional tracing, logging, and metrics layers to instrument your Effect application:

  import * as Sentry from '@​sentry/effect';
  import * as Layer from 'effect/Layer';
  import * as Logger from 'effect/Logger';
  
  const SentryLive = Layer.mergeAll(
    Sentry.effectLayer({ dsn: '__DSN__', tracesSampleRate: 1.0, enableLogs: true }),
    Layer.setTracer(Sentry.SentryEffectTracer),
    Logger.replace(Logger.defaultLogger, Sentry.SentryEffectLogger),
    Sentry.SentryEffectMetricsLayer,
  );

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• feat(astro): Add Astro 6 support (#​19745)

  This release enables full support for Astro v6 by adjusting our Astro SDK's middleware to some Astro-internal
  changes. We cannot yet guarantee full support for server-islands, due to a bug in Astro v6
  but we'll follow up on this once the bug is fixed.

• feat(hono): Add basic instrumentation for Node runtime (#​19817)

  Adds a new package @sentry/hono/node (alpha) with basic instrumentation for Hono applications running in Node.js.
  The Hono middleware for Cloudflare (@sentry/hono/cloudflare - alpha) comes with fixes, and it's now possible to access the Cloudflare Worker Bindings (env) from the options' callback.

  Start using the new Hono middlewares by installing @sentry/hono and importing the respective middleware for your runtime.
  More instructions can be found in the Hono readme.

  Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.

• feat(nestjs): Instrument @nestjs/bullmq @Processor decorator (#​19759)

  Automatically capture exceptions and create transactions for BullMQ queue processors in NestJS applications.

  When using the @Processor decorator from @nestjs/bullmq, the SDK now automatically wraps the process() method
  to create queue.process transactions with proper isolation scopes, preventing breadcrumb and scope leakage between
  jobs and HTTP requests. Errors thrown in processors are captured with the auto.queue.nestjs.bullmq mechanism type.

  Requires @nestjs/bullmq v10.0.0 or later.

• **feat(n